Refresh Update FAQ and add explanation about why a release could be missing from Update Assistant #1954
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Quetzacoalt91
force-pushed
the
add-php-requirements-in-update-faq
branch
from
7f99f76 to
b5957cf
Compare
Quetzacoalt91
commented
Apr 9, 2025
| - [The version of PrestaShop does not match the one stored in database](#the-version-of-prestashop-does-not-match-the-one-stored-in-database) | ||
| - [Restore access to Back Office Page](#restore-access-to-back-office-page) | ||
|
|
||
| ## The newer version of PrestaShop is not shown on Update Assistant |
Member
Author
There was a problem hiding this comment.
To ease the review: This question has been added.
| * The PHP version running the store does not match the required range. It will happen if PHP is either **too low** or **too high**. Ensure the [system requirements][system-requirements] are fullfiled. | ||
|
|
||
| First, identify what is the `slug` of the Back Office pages. You can find them into the SQL table `ps_authorization_role`. This will tell you the SQL identifier for these pages. | ||
| ## The version of PrestaShop does not match the one stored in database |
Member
Author
There was a problem hiding this comment.
This question has been moved up.
| ``` | ||
| [Ajax/Server operation [...]] textStatus: "Error" errorThrown: "" JqXHR: "", | ||
| ``` | ||
| ## Restore access to Back Office Page |
Member
Author
There was a problem hiding this comment.
This question has been moved to the bottom
| Third, check whether the table `ps_access` grants access to the Back Office pages, using the identifier of the role and the identifiers of the Back Office pages. There must be a record for the role and the page. If there is no such record, create it to grant access. | ||
| **A:** In PrestaShop, `PS_VERSION_DB` is a constant that holds the current version number of your PrestaShop database schema. The main purpose of `PS_VERSION_DB` is to keep track of the database schema's version history. When you update a shop, the database schema is modified to match the structure of the new version (e.g. add or remove tables, columns, or relationships). | ||
|
|
||
| ## Upgrade fails with Error message JqXHR |
Member
Author
There was a problem hiding this comment.
This question has been deleted.
Quetzacoalt91
force-pushed
the
add-php-requirements-in-update-faq
branch
from
b5957cf to
42fe45c
Compare
…issing from Update Assistant
Quetzacoalt91
force-pushed
the
add-php-requirements-in-update-faq
branch
from
42fe45c to
1d46e03
Compare
ga-devfront
approved these changes
Apr 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.